Bump body-parser from 1.20.5 to 1.20.6 - #2682
Conversation
Bumps [body-parser](https://github.com/expressjs/body-parser) from 1.20.5 to 1.20.6. - [Release notes](https://github.com/expressjs/body-parser/releases) - [Changelog](https://github.com/expressjs/body-parser/blob/master/HISTORY.md) - [Commits](expressjs/body-parser@1.20.5...1.20.6) --- updated-dependencies: - dependency-name: body-parser dependency-version: 1.20.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@copilot 1. rebase the branch with main |
…andling for the Blob and Queue services (#2675) * Updated npm package fixes * Updated changelog * Bump morgan and refresh audit changelog note * Bump service API versions to 2026-06-06 and update changelog * Bump axios/esbuild and update constants * Fix #2672: Handle GC startup errors during server initialization Fixes race condition where GC error during startup would attempt to close server while still in 'Starting' state, resulting in 'Cannot close server in status Starting' error. Changes: - Modified BlobServer and QueueServer error handlers to wait for server to reach 'Running' state before attempting close - Added timeout logic (up to 5 seconds) to wait for server startup completion - Gracefully handles case where server cannot transition to Running state - Allows Azurite to recover when encountering errors processing legacy persisted data from previous versions Fixes: #2672 * Add comprehensive test suite for issue #2672 - Added 4 test files with 10 total test cases covering: * Unit tests for GC error handler state machine (3 tests) * Blob server startup error recovery scenarios (3 tests) * Upgrade regression tests (2 tests) * Queue server startup error recovery scenarios (2 tests) - Tests validate: * Fresh start scenarios without persisted data * Graceful error handling during GC initialization in Starting state * Concurrent startup operations * Data persistence across upgrade scenarios * Multi-container and multi-blob scenarios * Recovery from timeout conditions - All 777 tests passing (including 10 new tests) - No regressions in existing tests - Full TypeScript compilation clean
Done. The branch has been rebased onto Validation completed on the rebased branch:
No additional build/test fixes were required; changelist is updated with the rebased commit. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 19 out of 21 changed files in this pull request and generated no new comments.
Suppressed comments (2)
ChangeLog.md:10
- PR title/description indicates a body-parser patch bump, but the changelog (and diff) show broader changes (npm audit fix across multiple deps + API version bump + GC/upgrade fixes). This mismatch makes it harder to review/release-track; consider updating the PR title/description or splitting unrelated changes into separate PRs.
## Upcoming Release
General:
- Applied npm audit fix to updates across multiple dependencies to address security vulnerabilities and maintenance updates.
- Bumped the default Blob, Queue, and Table service API version to `2026-06-06`.
.npmrc:3
- This repo-level .npmrc hard-requires authentication for every registry request (always-auth=true) but the CI workflow doesn’t set NPM_TOKEN. This can break npm ci for contributors/CI and also encourages keeping publish auth settings in the repo instead of scoping them to release pipelines.
registry=https://registry.npmjs.org/
always-auth=true
//registry.npmjs.org/:_authToken=${NPM_TOKEN}
Bump body-parser from 1.20.5 to 1.20.6
Bumps body-parser from 1.20.5 to 1.20.6.
Release notes
Sourced from body-parser's releases.
Changelog
Sourced from body-parser's changelog.
Commits
5cc4fb81.20.6 (#746)3492672fix: improve limit option validation (#741)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.